Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add working groups list to get_involved/get_involved.md #666

Merged
merged 3 commits into from
Feb 18, 2022

Conversation

NickleDave
Copy link
Contributor

Description

Adds a section ### Join a working group under # Ongoing contribution with a list of working groups and links to those pages.

Motivation and Context

The goal is to make sure anyone that wants to get involved knows the working groups exist.
As discussed in dei-wg meetings.

This would resolve: USRSE/dei-wg#1

I am sure this is a very first draft and people with more experience at US-RSE will have feedback.
Note that I put this section at the top of "ongoing contribution" because I feel like we might want to rank in terms of effort? Seems like the first thing we suggest to people should be something relatively low effort (e.g. compared to "Start Your Own Blog" ... but maybe this is just me being a failure as a blogger)

Checklist:

  • I have posted the link for the PR in the usrse slack (#website) to ask for reviewers
  • I have previewed changes locally
  • I have updated the README.md if necessary

cc @usrse-maintainers

will post link and preview on CI

@danielskatz
Copy link
Contributor

This looks good to me, though I wonder if we also should say that people with ideas that don't fit in an existing working group can ...

@mrmundt
Copy link
Contributor

mrmundt commented Jan 27, 2022

I agree with @danielskatz . This would be a great place to put a, "Don't see something you like here? MAKE YOUR OWN (How-to article to be created)"

@mtbc
Copy link
Contributor

mtbc commented Jan 27, 2022

Looks good to me too.

@NickleDave
Copy link
Contributor Author

This would be a great place to put a, "Don't see something you like here? MAKE YOUR OWN (How-to article to be created)"

@danielskatz @mrmundt I agree with both of you and thought about writing that

From today's outreach meeting notes, looks like we have a plan to draft a how-to before February?

Should we make an issue for that somewhere (outreach repo?) and then add a checklist on that issue that says "update link on Getting started page"?

If you agree I could (1) make that issue and (2) make the change here (maybe even with a link to the issue in the page?)

@vsoch
Copy link
Member

vsoch commented Jan 28, 2022

@NickleDave is there an outreach calendar invite? I didn't know it was today and I missed it!

@NickleDave
Copy link
Contributor Author

Yes I think @mrmundt is the person who has the power over the invite

@vsoch
Copy link
Member

vsoch commented Jan 28, 2022

okay I'm going to break my rule of only doing 1 working group at a time, but I definitely want to come to the outreach ones!

@vsoch
Copy link
Member

vsoch commented Feb 7, 2022

Ping @NickleDave lets make sure to finish this up this week it’s a great idea to add!

@NickleDave NickleDave force-pushed the add-working-groups-to-get-involved branch from 8fa7aa1 to 04e2f94 Compare February 7, 2022 15:22
@NickleDave
Copy link
Contributor Author

I decided to ask for forgiveness instead of permission.

re the comments from @mrmundt and @danielskatz above, I raised this issue in the outreach-wg repo:
USRSE/wg-outreach#1

And I added text incorporating your language that references the issue

@NickleDave
Copy link
Contributor Author

@vsoch is there some magic git incantation I can utter to resolve these conflicts?

I did git fetch upstream && git merge upstream/main but I am getting the weird complain about data/jobs.yml and I don't want to further bork it up

@vsoch
Copy link
Member

vsoch commented Feb 7, 2022

@NickleDave let me see if I can fix it.

@NickleDave
Copy link
Contributor Author

🙏 thank you @vsoch

@danielskatz
Copy link
Contributor

Is this ready to merge?

Copy link
Member

@vsoch vsoch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep!

@vsoch vsoch merged commit 21ac81f into USRSE:main Feb 18, 2022
@NickleDave NickleDave deleted the add-working-groups-to-get-involved branch August 24, 2022 20:05
@wsphd wsphd mentioned this pull request Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

add "Working Group" info to "Get involved" page
5 participants